Navigation API / Text Fragments: Implement User Involvement
Categories
(Core :: DOM: Navigation, task)
Tracking
()
People
(Reporter: jjaschke, Assigned: jjaschke)
References
(Depends on 1 open bug, Blocks 1 open bug, )
Details
Attachments
(1 file, 1 obsolete file)
The HTML Standard defines User Involvement. This is being referenced in the Text Fragments spec to determine if a text directive is allowed to be scrolled to. Gecko currently does not implement User Involvement.
Tagging this as "see also" instead of "blocks" for Bug 1753933 and Bug 1777171.
Assignee | ||
Comment 1•1 year ago
|
||
User involvement as defined in the spec is not implemented in Gecko yet.
Therefore, the changes introduced in Bug 1888756 disallowed scrolling to text directives if the load was triggered by the user, eg. by pasting a link with a text fragment into the url bar.
This patch checks if the triggering principal of the load is the system principal.
This is equivalent to the "browser UI" value of user involvement.
Updated•1 year ago
|
Assignee | ||
Comment 2•1 year ago
|
||
Here is a try run, in which this patch is based off of Bug 1888756 (which at this point of time is only in autoland, not in central).
Assignee | ||
Updated•11 months ago
|
Assignee | ||
Comment 3•11 months ago
|
||
(Let's use bug 1904773 for the makeshift solution and keep this one for a potential real implementation of user involvement.)
Updated•11 months ago
|
Updated•11 months ago
|
Updated•10 months ago
|
Assignee | ||
Updated•10 months ago
|
Assignee | ||
Comment 4•4 months ago
|
||
Assignee | ||
Comment 5•4 months ago
|
||
The attached patch switches the implementation of user involvement in Text Fragments from checking the triggering principal directly to using the user involvement flag, which is introduced in Bug 1942630.
At the moment this change makes a test fail because the logic how to set the user involvement has not been implemented yet (hence the WIP status).
Assignee | ||
Updated•4 months ago
|
Description
•